Skip to content
[Jenkins]Jenkins
log in

Test Result : Scenario: Negative scenario when client connects twice with same client id

3 failures , 10 skipped
13 tests
Took 57 ms.

All Tests

Test nameDurationStatus
And Client named "client-1-2" is connected0 msSkipped
And Client with name "client-1-2" with client id "client-1" user "kapua-broker" password "kapua-password" is connected0 msSkipped
And Disconnect client with name "client-1-2"0 msSkipped
And I wait 2 seconds for system to receive and process that message0 msSkipped
And I wait 2 seconds for system to receive and process that message0 msSkipped
And topic "$EDC/kapua-sys/client-1/MQTT/BIRTH" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"0 msSkipped
And topic "$EDC/kapua-sys/client-1/MQTT/CONNECT" content "src/test/resources/mqtt/rpione3_MQTT_BIRTH.mqtt" is published by client named "client-1-1"0 msSkipped
Given Client with name "client-1-1" with client id "client-1" user "kapua-broker" password "kapua-password" is connected0 msSkipped
Scenario: Negative scenario when client connects twice with same client id0 msFailed
Scenario: Negative scenario when client connects twice with same client id16 msFailed
Scenario: Negative scenario when client connects twice with same client id41 msFailed
Then Client named "client-1-1" is not connected0 msSkipped
Then Disconnect client with name "client-1-1"0 msSkipped